WEBVTT 00:00.000 --> 00:28.740 along with 00:28.740 --> 00:34.180 Hello everybody, my name is Tempama and you're listening to Hacker Public Radio Community News 00:34.180 --> 00:41.940 for March 2014. If you're new to the show, this is an opportunity for us to give you some 00:41.940 --> 00:47.460 updates as to what's been going on in the community that you might not know about. 00:47.460 --> 00:52.500 Joining me this evening is Dave. I'm living in Scotland, but I'm in English Morris. 00:52.500 --> 00:58.080 It's me, that's me. A live, that a live from northeastern 00:58.080 --> 01:07.280 west. Is it northeastern? Yes, it's the northeast, guenegan 착est. Mr. Puy, Puy Puy Puy Po T 01:07.280 --> 01:13.400 Thanks. Thanks, can I appreciate the intro and also here is NYU Bill. fue 01:13.400 --> 01:16.580 on the same mic though little bit. It's very and it's very 01:16.580 --> 01:20.260 directional, but I'll chip in here in there. Super, super, super. 01:20.260 --> 01:24.420 Hello, Mr. Moors. Hi, and why Bill, how are you doing? 01:24.420 --> 01:28.420 You're going, man. Did you guys actually meet when you were over? 01:28.420 --> 01:32.620 Oh, cast, yeah. Oh, oh, oh, camp, I mean. Oh, yes. 01:32.620 --> 01:36.100 The one I couldn't make. Yeah, he was, he was on the table with us. 01:36.100 --> 01:40.100 Hmm, I'm not sure what that means. 01:40.100 --> 01:46.980 Okay, very good. As we normally do, though, we will start off going through some of the 01:46.980 --> 01:53.220 shows that were on in the last month, given a quick commentary rundown, and bring you up 01:53.220 --> 01:58.820 to date on those. The first or not, we didn't know, just we normally introduced new hosts, 01:58.820 --> 02:04.020 but as there was no new hosts this month. Hello, people. Hello, those of you with guilty 02:04.020 --> 02:10.420 consciences, who haven't contributed to HPR before, now is an ideal time. If you go to the 02:10.420 --> 02:15.700 contribute or a calendar page, you will see a lovely diagram that's like a, like, a 02:15.700 --> 02:21.300 upturned soul would so. That goes up and then down and then goes up and then slowly down 02:21.300 --> 02:26.900 and opens slowly down. And it's now very, very, very sloping down. We could very much do 02:26.900 --> 02:32.980 with episodes in the next two weeks or so. So new hosts, please get your friend 02:32.980 --> 02:38.260 out and start doing some recordings, even they how I got into Linux show would be a 02:38.260 --> 02:43.540 excellent, excellent way to start. I'd like to request a topic here, Ken, if you don't mind. 02:43.540 --> 02:50.660 But I had Dave, can you email this to me? Yeah, all right. Secretary, I'd love to hear a show 02:50.660 --> 02:56.020 from anyone on, like, how much they like New Zealand. That would be cool, wouldn't it? 02:56.020 --> 03:00.180 Yeah, anyone at all, no one in particular, anyone in New Zealand would be fine. 03:00.180 --> 03:04.580 Randomly down there about life, things they've noticed. That's sort of thing. 03:04.580 --> 03:10.020 The ideal type of thing. Yeah, yeah, especially if the person is new to New Zealand. 03:10.020 --> 03:14.020 That's, but no one in particular. Exactly. Anyone at all, any of our listeners in New 03:14.020 --> 03:19.060 Zealand come on down on the prices, right? Actually, I have a topic as well, Dave, 03:19.060 --> 03:25.060 know that you're taking, talking anyway. I want to put a call out there to any 03:25.060 --> 03:32.420 hand radio enthusiasts on the network, and I know there are. I am interested in doing some 03:32.420 --> 03:37.620 study for my hand radio license, and I've been listening to lots of podcasts, and lots of the 03:37.620 --> 03:42.980 podcasts, either I don't know the correct podcast to listen to, in which case I'm requesting a 03:42.980 --> 03:53.940 show of hand radio podcasts, a rundown of them, or I'm looking for some hand radio professional 03:53.940 --> 03:59.620 people to come on, and we do a series where I'm the new, and you can do, you can be my 03:59.620 --> 04:06.740 elder, and see if we can figure out some of the hand radio stuff, because as I'm listening 04:06.740 --> 04:13.700 to the books, a lot of this will be very much of interest tackers. We had a request for a live show, 04:13.700 --> 04:21.140 or a live request here at the fest, too. Somebody requested a, how do I record a show for HBR, 04:21.140 --> 04:26.500 our tag team, where you have the teacher student type scenario? 04:27.780 --> 04:32.420 Okay, that'd be a good one. Yeah, I think Dave and I have we've done one of those. 04:34.420 --> 04:37.940 The parole thing where you were the teacher, obviously, and I was the dumb student. 04:39.220 --> 04:45.300 I think the answer is simply come on mumble, and if you don't have a technical expert with you, 04:45.300 --> 04:51.460 then find one on the mailing list, and if you are the technical expert and you're looking for 04:51.460 --> 04:57.540 a new, then again, come on the mailing list, and then just try and agree a time beforehand, 04:57.540 --> 05:08.260 and come on the HPR mumble list. Okay, but anyway, no harm to add that into the list of shows. 05:08.260 --> 05:16.100 So, quickly gone through the episodes, 1456 was released on the third of March, and it was 05:16.100 --> 05:23.380 HPR community news for January 24th, and an entire month later, obviously. Then we had 05:23.380 --> 05:31.220 bento with Zubuntu, Kylie, EPC, Mark, down stuff, Pogo, Pogo, Pogo, for a more, and the only thing 05:31.220 --> 05:37.460 only problem I have with this episode was stop, stop releasing all these in the same episode, 05:37.460 --> 05:43.060 two hundreds of different little episodes for me. But that was me with my admin hat on, 05:43.060 --> 05:49.060 it was very interesting to sit down, just here's somebody chatting about various different topics. 05:50.100 --> 05:53.700 Yeah, that's a whole week's worth of shows. There you go, that's what I was thinking. 05:55.300 --> 06:01.460 The only thing I would, about this Pogo plug for thing, I would be reluctant to advise Pogo 06:01.460 --> 06:09.380 plug to anyone. Due to the fact I bricked for them so, well, I'll not break for them, but for the 06:09.380 --> 06:14.740 same price, you can get a Raspberry Pi or there's plenty of other little devices that you can 06:14.740 --> 06:21.300 better a lot easier, a lot more open. And not talking from our MS point of view, I'm just mean a lot 06:21.300 --> 06:26.260 less hassle to get stuff on, and you have a more standard destroyer. I think I'd be willing 06:26.260 --> 06:31.780 to bet that Pogo plug is just as hesitant to recommend you. Well, the feeling is mutual. 06:34.420 --> 06:41.860 Anyways, free culture and open animation by CT, and again, I love CT's episodes, 06:41.860 --> 06:49.060 largely because of his hitship mouth. No, it doesn't love CT. This was, this was actually quite 06:49.060 --> 06:57.300 quite cool. He did a whole series of them out there, and this was where they wanted to put together 06:57.300 --> 07:07.620 a state of, you know, a collection of the various different open source movies and stuff together. 07:07.620 --> 07:14.580 And I think that's something, as I had a main use case for myself, where I work, we use test 07:14.580 --> 07:20.820 videos a lot, and having this creative common stuff that we can use that for encoding is really 07:20.820 --> 07:26.020 helpful because you can just give the movies to somebody and say, here, go check and make sure 07:26.020 --> 07:32.020 that works with those videos. So it's really cool. Nice to have a larger selection of stuff like that. 07:33.220 --> 07:41.140 Okay, the following day was 1459, deep geek, locational privacy and retro with retro check, 07:41.140 --> 07:46.820 the lowly pager, fantastic. Never thought of this old premise of the episode for those that 07:46.820 --> 07:52.740 didn't hear it was that you, um, obviously your phone is tracking you the whole time because 07:52.740 --> 07:58.660 there's a transmission receive and you're contacting the tower. So deep geek had the idea, 07:58.660 --> 08:03.700 well, go back to carrying a one-way pager, and the only thing they know is that you're in a particular 08:03.700 --> 08:11.140 region, and it's a broadcast mechanism without a return path. So therefore, um, nobody can track you, 08:11.140 --> 08:17.940 but I don't know. I had a quick look here in the Netherlands and it was very hard to get a service. 08:18.980 --> 08:23.140 Yeah, I was going to say it would be, it was surprised to hear that anyone still using one just 08:23.140 --> 08:29.140 because I didn't think any services still existed. And they do have one of my previous jobs, 08:29.140 --> 08:34.260 this worldwide pager is because of the guarantee that you were going to get the message in 08:34.260 --> 08:41.220 order and leisure. So yeah, that makes sense. But then again, I imagine that would be a two-way 08:41.220 --> 08:48.020 sort of thing. So hard to know. But an interesting interesting thought on the whole thing. 08:48.820 --> 08:54.500 And did I have, looks like I've got a HTML bug in that episode as all Dave, can you make notes? 08:54.500 --> 09:02.740 1515. 159, what's the problem? There's missing a closing HTML, a slash a tag. 09:04.500 --> 09:11.380 Okay, 1459. Right. And got a lot of you don't know. There was written a tool to check all this 09:11.380 --> 09:18.660 before I posted, but I still have a word. I still have a donut yet. If we had 1460, the road 09:18.660 --> 09:27.060 Roderior commands line combat life and this is Nightwise again doing SSH server on 09:27.060 --> 09:34.100 Ubuntu irsysi, Centinium, Alpine, ConnectBoss, Bot Sync, Putty, Secure Shell, and 09:34.100 --> 09:35.100 Nightwise.com. 09:35.100 --> 09:39.660 Wait a minute, you're saying that the command line is powerful enough to use in the road? 09:39.660 --> 09:41.860 I don't know if I can buy that. 09:41.860 --> 09:46.380 Well, there you go, you heard it here for first folks. 09:46.380 --> 09:55.060 But it is, it's also a very good list, and items for the requested topic would be setting 09:55.060 --> 10:00.060 up, I mean we have setting up SSH server, we've done this a few of those, this is like 10:00.060 --> 10:07.580 a nice one on an irsysi, and I like a nice one on setting up IMAP mail, and also setting up 10:07.580 --> 10:14.420 something like Gmail via IMAP on a command line, a command line mail program that you could 10:14.420 --> 10:22.860 run and putty for requested topics, then we had Dave with the FOSDM key signing event, which 10:22.860 --> 10:29.540 was very, very interesting actually from the point of view of how complex it is, and perhaps 10:29.540 --> 10:34.940 they should have thought a little bit more about how they were going to do it. 10:34.940 --> 10:43.100 Yes, they did, they did accept all the criticisms from the community, and I've been in touch 10:43.100 --> 10:48.660 with the guy who organized it, I pointed him to my episode slightly, check it out, yeah, 10:48.660 --> 10:55.580 yeah, he got a few things wrong by the way, so he got his own back, but yeah, so he's going 10:55.580 --> 10:58.620 to do quite a lot of changes for next year's thing. 10:58.620 --> 11:03.620 I think that's something that definitely needs to be done, it would be nice to be able 11:03.620 --> 11:08.220 to go in for like half an hour or something, it just could have done, but I imagine it's 11:08.220 --> 11:14.220 having a look at the CAsert, there is a amount of time that's required to give the level 11:14.220 --> 11:17.580 of trust that you need in order to do something like that, and it's a function of the 11:17.580 --> 11:22.500 number of people as well, which is where things get really unwieldy, yeah, absolutely, 11:22.500 --> 11:23.500 absolutely. 11:23.500 --> 11:28.620 I want to get the majority of the executive signatures you can, would be, yeah, I was just 11:28.620 --> 11:32.300 thinking it might be something to be doing around lunchtime so that people got ease 11:32.300 --> 11:37.940 and you know, be doing that sort of thing at the same time, yeah, yeah, that's true, 11:37.940 --> 11:41.940 it'd be quite nice to have somewhere sit down, actually, to have a substitute up in 11:41.940 --> 11:46.820 around in a circle, in a corridor, but I'm kind of especially when you get a little bit, 11:46.820 --> 11:52.420 you know, longer in the tooth, yeah, I also wanted to be dark and stuff as well, yeah, 11:52.420 --> 11:54.940 getting special pleading on my path. 11:54.940 --> 12:01.100 And the following day, we had a 1462 encryption and email with Ponderberg, and as you all 12:01.100 --> 12:08.580 know, doubt have noticed, because I fixed it about 20 minutes ago, and the series information 12:08.580 --> 12:16.980 is fixed and back on the website, so this is in the privacy and security section. 12:16.980 --> 12:22.940 And making all of them, I want to talk about that later on in the episode about series's 12:22.940 --> 12:29.020 and stuff, you wouldn't mind reminding me, yep, okay, we'll do this was a hookah about how 12:29.020 --> 12:33.580 to set up encryption, email with Ponderberg, which is actually one I listened to, broke my 12:33.580 --> 12:37.460 own rule, because this was something that was in the queue that I actually needed to do. 12:37.460 --> 12:42.140 Yeah, I learned a few things from this, I have to say, but I knew how to use Ponderberg 12:42.140 --> 12:46.020 encryption, but covered it in love depth, that was very good. 12:46.020 --> 12:53.460 Yeah, the following day, 1463 code is a life-sucking abyss, also my story, now given 12:53.460 --> 12:59.260 this was sickflop, and we all know her history of sending in interesting episodes, I was 12:59.260 --> 13:04.540 hoping that this would be a positive one, and it turns out to be a very positive one, and 13:04.540 --> 13:11.780 I'm very happy for sickflop, and yes, I think we've all been here at this to some level 13:11.780 --> 13:19.500 of another, basically, four o'clock in the morning, and just one more bug to fix, or for 13:19.500 --> 13:29.500 example. Why won't this script run exactly? Wait, they won't even give me a damn error. 13:29.500 --> 13:39.260 And the next day, 1464 HBR audio book club is revived from the depth, from the depths 13:39.260 --> 13:45.660 is space, casey, featuring the HBR audio book club members, and featuring the author 13:45.660 --> 13:49.740 herself, who was on the show. Yeah, Cristiano Ellis, that was a lot of fun. 13:49.740 --> 13:54.540 I went down very well, almost. Well, thank you. It's funny, too, you say it rose from 13:54.540 --> 13:57.380 the dead, and I think the previous two before that were the zombie ones, maybe this 13:57.380 --> 14:05.140 should have been another zombie one. Very good, very good. The one thing about the boot 14:05.140 --> 14:11.500 club thing is, I think it's hitting with the international aspect of HBR that the 14:11.500 --> 14:16.820 community uses, and that is, I think a lot of people, namely, I would have liked to give 14:16.820 --> 14:23.660 some feedback on to this episode, because my feedback was that I found it very, I, after 14:23.660 --> 14:30.220 the last book club, I had listened to this book and reviewed it, and ended up having 14:30.220 --> 14:34.700 a memory of the book as being something just a horrible horrible book that I never wanted 14:34.700 --> 14:38.300 to listen to again. And then when it came up again, I thought, okay, well, I better listen 14:38.300 --> 14:43.180 to it again for this episode, and as I was listening to it, the whole way through was going, 14:43.180 --> 14:46.940 hey, this is actually a good book. Why did I hate this book so much? And then at the 14:46.940 --> 14:54.380 last chapter, that's why I realized why I hated the book so much at the very end. So if you 14:54.380 --> 14:57.980 have listened to this episode, listen to this discussion about this, but I would have liked 14:57.980 --> 15:03.260 to give that feedback, but it's not possible with the timing, it's simply not possible with 15:03.260 --> 15:08.860 all our people. So I wonder, would there be a way that we could do a two minutes, the people 15:08.860 --> 15:16.220 could send in the reviews, that you could add them to the show in between the preview and the 15:16.220 --> 15:22.780 beverage thing? We've done it before. Well, so I invite everybody to do that. The next book 15:23.500 --> 15:31.660 is going to be Sean Montale's number one, South Coast, which I have read and he is a brilliant 15:31.660 --> 15:37.740 book. I do think I have to delay the recording of that show by about a week, just because all the 15:37.740 --> 15:44.780 enough stuff is going to have me busy. Absolutely, but you should put out a list. Yes, I keep 15:44.780 --> 15:49.980 meaning to. No, but what I mean to say is put out a request for the people who cannot turn up 15:49.980 --> 15:56.460 to send in the recordings by then, because you want at least a week or two to play them on the show. 15:56.460 --> 16:02.300 Yeah, yeah, no, that's a good idea. I appreciate it. So cool. All right, moving on, following day we 16:02.300 --> 16:11.500 had Librofus, right, a brochure project and this is a hookah, doing a brochure for HPR and if you 16:11.500 --> 16:15.900 want to have a look at that, it's downloadable from the website. Dave, if you could make a note 16:15.900 --> 16:23.660 that I put this somewhere for actually on the website that needs to be a festival going to a festival 16:23.660 --> 16:32.460 link or something. His Librofus series has made me a hero to my life again. There is a while where 16:32.460 --> 16:39.900 she didn't think I could do much with computers anymore, but this saved me. Excellent, excellent. 16:41.020 --> 16:46.780 Okay, I could go so many ways with that, but I'm not. I feel free and it's probably true, 16:46.780 --> 16:52.060 whatever you're thinking. Anyway, the following day we had you with you polky with 16:52.060 --> 16:59.980 thoughts on GPS's. Oh, yeah. That was an old recording, actually. That was recorded from last summer 16:59.980 --> 17:06.300 and I took me a long time to edit it, just to get off my ass and do it, which I'm a little embarrassed 17:06.300 --> 17:12.620 about, but I hope you liked the episode. Yes, I did actually. I liked it very much and you had some 17:13.660 --> 17:20.700 comments about to the show about from Ron who owned an N900. And 17:20.700 --> 17:25.820 this was day one where you were talking about the Tom Tom and that sort of thing. Yes, Sir. 17:25.820 --> 17:31.580 And I also, Dave, I know you just keyed up, but we didn't hear anything you said. Sorry, my, yeah, 17:31.580 --> 17:37.340 I think my sound a little bit funny here. I was just going to say the thanks for the hints about 17:37.340 --> 17:42.060 the Tom Tom, because I've been thinking about buying one of those, I think I'm not going to do. 17:44.060 --> 17:47.980 Yeah, well, like I've said it before and I'll say it again, if you can find one used for 17:47.980 --> 17:54.380 half price, go for it. Don't pay full price. Well, you have another episode in the mix, 17:54.380 --> 18:03.020 and I want to just hold off my comments on this. So, okay, I did want to say one more thing about 18:03.020 --> 18:11.100 it, sorry. Who had the question? Yeah, the episode that David Whitman and I did together, 18:11.100 --> 18:16.300 he did all the recording and editing, so I insisted that he got the credit for it. But he wanted 18:16.300 --> 18:23.980 to do that on Osmond, and it was, I wanted this one, this GPS one out before the Osmond one. 18:23.980 --> 18:27.980 So, he was the real motivation for me getting those two or three shows out. 18:28.780 --> 18:34.380 Yeah, sometimes it's no harm to have somebody reminding you about new under pressure. 18:34.380 --> 18:40.300 And if anyone wants to do that, just, very simply, just send an email to the mail list, asking 18:40.300 --> 18:43.340 for a particular date to be booked about something and we'll happily do that. 18:43.340 --> 18:51.420 Nice. And you come on with how to win find the difference games. This is actually pretty cool, 18:51.420 --> 18:57.740 so I like a nice five minute show. Yeah, it was a silly one. I didn't know if people would be 18:57.740 --> 19:02.860 amused. He had me, like, making my eyes out of focus while I'm driving, trying to practice it. 19:04.700 --> 19:07.740 Yeah, someone, someone, I forget who it was, no, I'm going to have been jazzed or made the 19:07.740 --> 19:12.140 comment on status net that he liked the show. He said, I liked your HPR show, and I said, 19:12.140 --> 19:15.260 which one I just did too. He said, the one that you had your eyes crossed. 19:15.260 --> 19:18.700 I said, and I'm thinking, well, no, it's actually, I uncrossed my eyes. 19:18.700 --> 19:23.180 Did you just the opposite of how you make those things work? Yeah, exactly. Yeah, that's pretty cool. 19:23.180 --> 19:28.860 Did you get it to work? Did it work for you? For me, yeah, I do. I have done that, yes. 19:28.860 --> 19:32.300 And have you found one of those games and given it a try? Nope. 19:32.300 --> 19:38.060 Oh, all right, then. You did your show notes, lacked any reference to any games, so. 19:38.060 --> 19:43.260 Well, there's one for Android called Find the Difference. I didn't want to name anything 19:43.260 --> 19:47.020 particular, but I figured if you did that search, it'd come up with at least that one. 19:47.020 --> 19:53.260 But, yeah, if anyone tries this and it works, I'd love to hear about it. Go ahead and use the 19:55.500 --> 19:59.980 the feedback system on the website, which, oh, I don't know if I said it already, 19:59.980 --> 20:03.260 but also here today, so when made the suggestion that we should 20:03.260 --> 20:08.780 can ask your wife to record a little bit that we can add to the outro, 20:08.780 --> 20:14.460 that just says, you know, please leave feedback on the page for the episode, 20:14.460 --> 20:18.060 because I think a lot of people don't know that we have a feedback system at all. 20:18.060 --> 20:25.340 Yeah, that's, yeah, I haven't been publicizing the feedback system largely because it is 20:25.340 --> 20:31.740 a nightmare to administer and it actually logs every person who comes to the website with their 20:31.740 --> 20:37.260 IP address, with their browser type, it's just a horrible, horrible piece of code, 20:37.260 --> 20:44.220 which I'm going through today, trying to, so if anyone has any good suggestions for how we can 20:45.020 --> 20:52.300 in my grace to a common system that's simple to use, and that respects people's privacy, 20:52.300 --> 20:55.740 then I'm open to suggestions on the mailing list, of course. 20:55.740 --> 21:00.220 I don't know about privacy, but a forum would take care of the rest of the 21:00.220 --> 21:06.540 parts, but that's, you know, another thing. But as long as we do have the comment system that we do 21:06.540 --> 21:12.620 have, could we put the link back on the, the P in the, you know, Hacker Public Radio in the website 21:12.620 --> 21:17.340 title, where you could click on the P and see all the comments? Yeah, sure. Yes, email me a reminder, 21:17.340 --> 21:24.060 of course. Sure, I'll do that right now. And also, there was a, you asked about forums, but there 21:24.060 --> 21:31.740 is a, over on, been rev, every episode has a forum link, so if we could, we could put that in there. 21:32.300 --> 21:40.220 Okay, you can just go so over there, but it's, it's kind of no link, quick and easy link over to that. 21:40.220 --> 21:44.860 Actually, that's something we could probably do. I'll have to think about that, but, you know, 21:44.860 --> 21:51.020 I don't know if people, people mentioned discussed before, that seems to be a nice one, 21:51.020 --> 21:57.580 but, you know, whatever, whatever, I'm in the, I'm in the market for getting rid of this discourse, 21:57.580 --> 22:02.860 can't not discuss discourse and why we'll say it. Thanks, thanks to it. Okay, let's move on. 22:02.860 --> 22:09.260 A whole lot of nothing, Chromebook and of life sent to us WTF, non mainstream new links, 22:09.260 --> 22:15.580 just goes on more by bento, another one bento that you should cut up into little episodes and 22:15.580 --> 22:21.020 put them in, and that's the only thing that's the only criticism I have with, with this topic. 22:22.700 --> 22:30.140 I'm currently struggling with Chromebook myself, so I, there may be an episode about that later on. 22:31.340 --> 22:38.220 The following day, we had community news for February and more on that and on and then we had 22:38.220 --> 22:43.740 one of my backup shows, which were released into the main queue more on that and on, 22:43.740 --> 22:49.660 called learning to read the time with CC clock. Haven't had a chance to listen to this one yet, 22:49.660 --> 22:54.140 but I'm looking forward to it, it needs to go ahead of the rest of my queue. 22:54.140 --> 23:00.300 Nostal, so then the next day we had encryption stuff with blowfish by Sigflup, 23:00.300 --> 23:04.220 nice little short episode, filed it on the privacy and security. 23:05.180 --> 23:11.260 And again, I'm glad to be here and more from Sigflup. Yeah, and then we had Sig prompt with a 23:11.260 --> 23:17.580 backup show released, how we got into Linux, which was kind of interesting actually, always, 23:17.580 --> 23:25.740 always nice to hear. And then Dave Morris, with also an interesting discussion with Tom, who I 23:25.740 --> 23:31.180 only very briefly met as a foster, I feel really quite guilty about that actually. 23:31.980 --> 23:36.220 We're a busy guy, it's not a problem. Yeah, we've been trying to, 23:36.220 --> 23:40.700 I thought, wouldn't be great when we get back from fostering, we have a little chat about our experiences 23:40.700 --> 23:47.100 and record it. It took about a month or something before we got spent, it's just time and 23:47.820 --> 23:54.460 general failures on my part, so got there in the end. Yeah, exactly. We're very good, very good. 23:55.420 --> 24:04.300 Then we had 1474 behind the curtain look at OSM and OSM automation, automation, 24:04.300 --> 24:11.660 navigation directions with Polky and David Whitman, who I hate it because I already have 24:11.660 --> 24:18.540 a episode on my recorder that has not been edited, about OSM Android and he went ahead and did 24:18.540 --> 24:25.580 a far better show than I did, so I hate you, Polky. Oh, man, you should have put yours out first. 24:25.580 --> 24:30.140 No, no, no, then this would be embarrassing. You know, the thing, this is a real kick in the 24:30.140 --> 24:38.380 pants, too, because that episode was not live for an entire week before Osmond revved the whole 24:38.380 --> 24:44.380 you, well, a good portion of the UI, so we might have to do an update. Yeah, I know, let's say 24:44.380 --> 24:50.140 that is an absolutely brilliant piece of software, and I can probably say here what my episode was 24:50.140 --> 24:57.260 all about. I was driving back in Ireland and so I had all the map downloaded on OSM Android and 24:57.260 --> 25:03.420 was the first in OSM and was Osmond. I always called it OSM Android in my head, but on 25:03.420 --> 25:10.860 it was Osmond. And I had no clue, I hadn't used it at all, didn't know anything about it, 25:10.860 --> 25:14.620 because I was relying on Google Maps, and that was fine around where we were, but then we 25:14.620 --> 25:19.420 started going in between the hills and stuff. And suddenly all I was hearing was recalculating 25:19.420 --> 25:26.060 direction, and you know, a cached for I left the very detailed page into like a big zoomed 25:26.060 --> 25:33.980 up bit map of huge roads where it hadn't downloaded, that they, it couldn't keep up with the 25:33.980 --> 25:41.900 with where I was, and then there was a roadblock and trying to contact the server, 25:41.900 --> 25:47.020 kind of contact the server, so I couldn't, it couldn't, had not clue where I was, so then I opened up 25:47.020 --> 25:53.740 Osmond and it didn't recalculating, well, go this way, fine, probably directly there, so since then, 25:53.740 --> 26:02.460 I'm a big believer in this. I've been a big advocate of offline computing since probably 1996, 26:02.460 --> 26:07.500 when I couldn't afford to pay for dial-ups, service anymore, and had to just rely on whatever I 26:07.500 --> 26:13.260 already had on my computer desk and on CD, so it's, I fell right in with Osmond. 26:13.260 --> 26:18.380 And you know, people think that's, yeah, that's just because, you know, you're out in the sticks 26:18.380 --> 26:22.700 and in Ireland and you know, in a part of the country where you're going through hills and 26:22.700 --> 26:28.460 valleys and there's no no chance measures and stuff, but every day I travel through the most, 26:28.460 --> 26:33.660 you know, some of the most density populated part of the Netherlands and through the financial 26:33.660 --> 26:39.900 district to get to work, and every time you approach there, you have zero coverage, zero coverage, 26:39.900 --> 26:43.980 and half my train journey is zero coverage, and then there's a little bit of coverage, and then 26:45.180 --> 26:52.220 we go through a the train travels from there around to a public, you know, national park type area, 26:52.220 --> 26:57.420 or, you know, nature reserve, and of course there's no coverage there either, so you go from 26:57.420 --> 27:01.340 they're not being enough transmitters to being loads and loads of transmitters, but because there's 27:01.340 --> 27:07.740 so much congestion you're not getting through, so OSM and Osmond is really for mapping, 27:08.540 --> 27:15.260 and navigation is just very useful. Yeah, I need to probably submit a bug to them because 27:15.260 --> 27:21.500 with this rev, they changed the routing algorithms and they're not as good as they were a week ago, 27:21.500 --> 27:27.820 and I find that very upsetting, so I don't know what they are going to do, but I'm very sad 27:27.820 --> 27:31.820 that they're not working as well as they were, but I did use it to get here today, I used it, 27:32.860 --> 27:36.780 you know, I found the good parking lots around here, the free one, I put them on the map, so 27:36.780 --> 27:40.700 they're ready for just anybody to be able to find them and a couple of people have already asked me, 27:40.700 --> 27:44.380 hey, where's the free park and for an elf today, so I've been able to just go, hey, 27:44.380 --> 27:48.620 pull up OSM and there it is. Yeah, that cool thing about it is you really need to use the favorites 27:48.620 --> 27:55.340 because the streets and sections don't really work that well, so I normally just go 27:55.340 --> 28:00.940 faring far out where I want to be and then put that in, you know, before I leave the house and then 28:00.940 --> 28:06.700 you're good. Yes, definitely, if you're using OSM and on short notice, that's the way to do it. 28:06.700 --> 28:12.300 If you've got more time, if your trip is in a month from now or more, so that there's time for 28:12.300 --> 28:16.940 OSM into rev, it's mapped data, you can put the building on there and put the street number and then 28:16.940 --> 28:21.100 it pulls right up all the time, but that does take some time for them to, I've talked about all this 28:21.100 --> 28:26.140 already, sorry. Yeah, no, cool. I happened to like it and enjoy the sort of topic, so we're good. 28:27.180 --> 28:32.060 Following day, we had a hookah with his introduction to spreadsheet, so he moved from word to 28:32.060 --> 28:38.860 calc and again starts that's really nice history about what a spreadsheet is and yet again I'm 28:38.860 --> 28:45.740 surprised by a story which I thought I had a fairly good understanding of and has been 28:45.740 --> 28:52.460 completely explained and I like a hookah's way of doing stuff and I guarantee you that they're 28:53.180 --> 28:58.540 put this stuff on a DVD and print out a little brochure with some screenshots of how he's talking 28:58.540 --> 29:05.340 about basically they his blog post and he has, you know, something that he could sell and people would 29:05.340 --> 29:14.780 buy. Yeah, for sure. And then for the last one, for this review is 147 T6 SEGA Genesis Music Driver, 29:14.780 --> 29:18.140 I had another one by SIGFLOP and this was a brilliant interview. I have 29:19.180 --> 29:26.140 new, it's good to know that SIGFLOP has some people that she can talk to on her own level, 29:26.860 --> 29:33.100 so because that didn't mean me, that's for sure. Heavy there, if you guys had a look at that 29:33.100 --> 29:37.900 the demo that she did the interview on a few months ago, several months ago now. 29:39.020 --> 29:44.700 No, no, I still have to do that. It's the way they described things with so amazing. I keep 29:44.700 --> 29:49.180 forgetting it's on my to-do list, but once it's on my to-do list that usually gets filed behind 29:49.180 --> 29:54.780 other things, so terrible at that. Not a problem, send the mail to the mail to the mail to the 29:54.780 --> 30:02.380 mail list for my booking to review that. It's delegation for you can, that's good. 30:03.180 --> 30:12.620 So just go over the comments on some of these shows, the Deep Geek commented on the HBR community news 30:12.620 --> 30:21.500 that they original set points were thought to be human body temperature. And then we had 30:23.180 --> 30:31.820 a ongoing reply from, from in relation to your episode with a journal and 30:31.820 --> 30:40.780 and, um, Sly, Sly, Sly, Sly. Still, still, still still. Still, still. Yeah, that's him. And you're 30:40.780 --> 30:46.700 basically having an ongoing discussion about whose rise now is wrong? Well, okay, I'm not going to, 30:46.700 --> 30:51.660 I'm not going to do him the disservice of misquoting him here, but he did leave a comment on there 30:51.660 --> 30:56.540 and I'll paraphrase, and then he knows. Okay, please. Yeah, because I was just trying to look 30:56.540 --> 31:03.020 it up, go ahead. Yes, yes, this is a bug. If there's no, not a GUI way to do thing, do a thing 31:03.020 --> 31:09.500 that a user wants to do. I am of the opinion, that the advantage of Ubuntu being widely popular all 31:09.500 --> 31:15.900 around the world are advantages that I want to see much better hardware support, much better. 31:15.900 --> 31:21.740 So for support, no longer being a second-class system, many things. Animals, people are not 31:21.740 --> 31:27.900 interested in using this CLI and teaching them to do, so is the wrong approach. Emphasis is 31:27.900 --> 31:35.740 mine. As you say, it is perfectly possible to win with free software, to love free software, 31:35.740 --> 31:42.300 to be passionate advocates without caring that somebody else loves proprietary software, 31:42.300 --> 31:48.940 but not everybody does. And the people who cascade, you make the environment so unpleasant that 31:48.940 --> 31:53.980 they're what drive you out. It seems that they quote advocate open source, quote, 31:53.980 --> 32:00.540 model has become for some people, they quote, chastise those who are insufficiently dedicated 32:00.540 --> 32:07.100 to the open source model, quote, model. And hearing that all the time is very, very tiring. It does 32:07.100 --> 32:12.540 matter if there are a hundred nice people for every one nasty person because you never get to hear 32:12.540 --> 32:18.220 from the nice people, just a nasty one. And there is no culture of nice people calling you out, 32:18.220 --> 32:22.300 calling out the nasty ones and stopping them doing it, because there is nice people looking 32:22.300 --> 32:29.020 insufficiently dedicated and so becomes a target of the ZLSI2 to which you replied, shall I read it? 32:29.820 --> 32:37.500 I can do this. My reply was, uh, still I cannot disagree with you more. At the time of this writing, 32:37.500 --> 32:40.860 and I didn't disagree with everything I should have specified here, but didn't. I didn't disagree with 32:40.860 --> 32:46.460 everything he said. But at the time of this writing, HPR has almost 1,500 episodes, 32:46.460 --> 32:50.940 almost all of them are dedicated to advocating free and open source software, 32:50.940 --> 32:56.940 gunulinics, open standards, and or free culture, and almost all of them, I cannot think of any 32:56.940 --> 33:03.740 exceptions, are hosted by nice people being nice. I'm familiar with the attitude that you're describing, 33:03.740 --> 33:09.900 but I think it is the exception these days. I'm somewhat of a late comer to Linux and free software, 33:09.900 --> 33:16.860 2007-ish, so maybe I'm not an acceptable measuring stick, but I don't even remember a time when 33:16.860 --> 33:24.620 that attitude was the rule. Agreed. So there was an anonymous commenter here today who stated that 33:24.620 --> 33:32.700 the Arch Linux forum may be what Sil is talking about. Okay, okay, it was X-1101. He's saying I can't 33:32.700 --> 33:41.580 go out. Okay, fair enough, but I personally haven't seen that, and it would also say that when people 33:41.580 --> 33:47.900 point you to the command line, if you have somebody in your neighborhood who is running Ubuntu, 33:47.900 --> 33:52.540 and there's somebody else who's running some other distro, and there's somebody running Ubuntu 33:52.540 --> 33:57.900 has a problem, and the other person is running another distro, and doesn't know how to do it via 33:57.900 --> 34:03.420 Ubuntu's specific way of doing it. Oh, then they're wrong, because it should be the Archway. 34:03.420 --> 34:08.060 But listen, then I'm kidding. I'm not an arch user, I'm kidding. 34:08.060 --> 34:14.460 The person running Fedora, for example, does not have a way to install well, or to install not 34:14.460 --> 34:20.940 well, and to install their display manager, because it's not packaged or whatever, to find out 34:20.940 --> 34:25.660 how to do it, do you want to weigh? Because the Ubuntu way is not the generic, 34:25.660 --> 34:31.020 everybody else in Linux way is. If Ubuntu had installed all their tools and pushed them 34:31.020 --> 34:35.420 upstream to all the distribution, all the desktop environments, so that there were standard 34:35.420 --> 34:41.820 on the desktop environments, if Ubuntu had done more work on the free desktop, standard, then there 34:41.820 --> 34:47.580 would be more chance that the way that they're describing to do stuff would be available 34:47.580 --> 34:52.780 on all the distributions. Therefore, allowing a person who is running X distribution that is not 34:52.780 --> 34:58.860 Ubuntu to help the person who is running Ubuntu. Because that has not occurred the only way that 34:58.860 --> 35:04.460 person running a distribution that is not Ubuntu can help somebody who is running Ubuntu 35:04.460 --> 35:11.980 is by doing it on the command line. That is not being nasty, that is not being on user friendly, 35:11.980 --> 35:18.860 that is helping your neighbor. That's a good point. Okay, that's all I'll say about that. 35:18.860 --> 35:27.100 Sorry, and this is, and we were talking about this today here at Nelf. This is when it came 35:27.100 --> 35:34.380 up that again, that I thought that a forum would be really nice to have. Yeah, a lot faster, 35:34.380 --> 35:41.980 because I think when did Stuart leave that comment? It was, geez, back in early 35:43.660 --> 35:48.300 February, maybe, and I think I didn't reply until April, because I just didn't know it was there. 35:48.300 --> 35:52.620 It doesn't get bumped. It doesn't get moved to the top. Whereas if we had a, if it was a forum, 35:52.620 --> 35:58.300 and each show had its own, you know, forum entry, its own thread, that would have gotten bumped, 35:58.300 --> 36:02.300 and people would have had the opportunity to comment on it and reply to that. 36:02.300 --> 36:06.380 Yeah, there is an RSS feed for those comments to Jeno the? No, I didn't. 36:06.380 --> 36:11.420 Okay, and go to the feed section. There's a library of SS feeds, so you can get that information out. 36:13.180 --> 36:17.100 That's something we need to look at anyway, but it's also, there's also a delay, 36:17.100 --> 36:23.420 because everything is moderators. For every one comment we get, we get about 10 spam 36:23.420 --> 36:29.340 comments as well. So I moderate everything. So there's a delay there as well. But again, 36:29.340 --> 36:33.180 suggestions for how we can improve the commenting system would be a good thing. 36:33.820 --> 36:42.060 Then we had a Claudio M was commenting on the, on the, on Siglook episode. 36:42.060 --> 36:46.860 And we had an all-comment on your episode, Dave, actually. 36:46.860 --> 36:56.860 Was it, no, on Chescriven's Templar, static HTML generator, by the, by what appears to be 36:58.140 --> 37:02.780 somebody Steve Kempe, who seems to be involved in the project. 37:03.660 --> 37:10.540 We had Delta Ray given another heads up to a good shout out to Siglook on her episode. 37:10.540 --> 37:15.660 We had Ron talking to you about the N900, and we've already discussed that. 37:18.060 --> 37:23.500 We had a, on the whole lot of nothing from book end of life sent to us mainstream and 37:23.500 --> 37:29.900 existuous by bento. We had about, I think it's better or better. I don't think it's bent, 37:29.900 --> 37:35.820 I don't think it's an end in there. Oh, sorry, Peter. Sorry apologies. You know, no new host this 37:35.820 --> 37:41.980 month, and I still end up butchering people's names. And you know, what can we be using 37:41.980 --> 37:45.980 use if I didn't put you somebody's name. And you're bedrock Lennox, yes, the lead developer of 37:45.980 --> 37:52.940 bedrock Lennox was on about the bedrock Lennox design and basically wants to point out 37:55.100 --> 38:02.620 that the bedrock uses changes behind the scenes is completely abstracted away. So I have 38:02.620 --> 38:11.980 to read those comments. David L. Wyns, then commented on episode 1463, which is again, 38:11.980 --> 38:21.180 Siglook code is life sucking a base, also my story. And my, I have moment, I have a problem 38:21.180 --> 38:27.180 moment was for a shivering in the garage thinking, I really should go to bed soon. 38:27.180 --> 38:31.660 I have to work in a couple of hours. Yes, I think we've all been there. And then the discussion 38:31.660 --> 38:41.340 about the end 900 from about you and adventure boy was commenting on episode 1434, 38:41.340 --> 38:48.540 why image in the free count Android, which we had on the 38th of January, but to tojit. 38:49.420 --> 38:54.460 And he is also planning setting up his next seven in a similar way. 38:54.460 --> 39:04.860 That's, do Reynolds posted on 1469, which was the community news episode. 39:08.460 --> 39:14.940 That's, we could do get more people involved in the community news. I want to be talking about 39:14.940 --> 39:26.460 that later. He also commented on a liberal exposure project, giving a shout out to Ruka, of course. 39:27.180 --> 39:37.260 And then Jonas commented on 1479, asking safeflops some questions about blowfish, and she replied. 39:37.260 --> 39:45.340 And then you were going, um, uh, to the, it's comments to the OSI Lair 3, 39:47.180 --> 39:52.380 hanging, hanging. Which we'll talk about in a while. And then we had polky, 39:53.820 --> 39:59.020 yes, making the comment about the update. So that's basically the comments. 40:00.060 --> 40:03.180 We have to wait to talk about that one, huh? Yeah, that's next month. 40:03.180 --> 40:08.060 Okay, did anybody ever get back with that poor fellow who got tricked? 40:08.060 --> 40:12.460 I got bad amount of mail. No, no, he, he, he tweaked this as well. He tweaked this as well. 40:13.660 --> 40:16.460 I just don't think, oh, I don't think he had enough coffee. 40:18.780 --> 40:23.340 Yeah, I got fooled by an April 4th this year too, did anybody else get on? 40:23.340 --> 40:43.180 No, we're getting comments in the room. Somebody else got, whoa. Okay, so someone else got tricked this April. 40:43.740 --> 40:48.700 I got one in a podcast where they replaced one of the hosts and, uh, filled in a new guy. 40:48.700 --> 40:55.100 And I totally believe that it was very sad too. Did you guys hear what she said? No. No. 40:55.100 --> 40:58.860 Oh, sorry, there's a, there's a young lady here from HP. And when I asked that, 40:58.860 --> 41:06.380 she's across the room. She piped up that, um, she logged into IRC on Monday. And somebody asked her, 41:06.380 --> 41:11.420 did you hear? They're re-licensing the Linux kernel under GPLV3. And she was pretty stunned. 41:12.140 --> 41:17.660 Yeah, that's pretty, so, um, yes, sorry, the green, she news if we, if we can. 41:17.660 --> 41:23.820 Sorry, sorry, sorry, I mean, she used that's what we're doing. Sorry, they, uh, mailing list if we can. 41:23.820 --> 41:25.420 Yeah, Sue. 41:26.460 --> 41:31.100 Well, a little bit of community news on, on that note while you're looking that up is, um, 41:31.100 --> 41:37.260 the hacker public radio community owned Zoom H1 showed up at my house, uh, I think last week 41:37.260 --> 41:42.060 or the week before, doing interviews with it today. So that will, that is now part of the, 41:42.060 --> 41:46.860 uh, official HPR conference kit. Sorry to the witch. Zoom H1 handheld. 41:46.860 --> 41:52.540 Oh, the real recorder. That is very nice. Very nice. How do we, uh, managed to afford that? 41:53.580 --> 41:58.540 Mostly David Whitman, a little bit of 51, 50 and a little bit of myself, I think. 41:58.540 --> 42:04.540 Oh, well, done. Thanks guys. Big shout. That is a really, I have a Zoom H2, which I'm using right now. 42:04.540 --> 42:12.940 And any thing that, um, uh, the reason my voice sounds as good as it does is because of this, 42:12.940 --> 42:19.660 is this really, uh, works very well. Yeah. I was just playing around with it earlier this week and 42:19.660 --> 42:24.860 just recording as I walked around the house and played back and was experimenting with the stereo 42:24.860 --> 42:32.780 effect. And the noise, the sound quality and reproduction and the stereo effect is so good that 42:32.780 --> 42:38.780 when you listen to it, played back, it's uncanny. You almost get vertigo or, or deja vu from it. It's 42:38.780 --> 42:44.380 got really, really stunning. And if you want to play with this Zoom H1, it no costs to you. 42:45.100 --> 42:51.100 All you have to do is, is, uh, be the conference guy in your areas or conference, uh, lady, 42:51.100 --> 42:55.980 and get the HP or conference kit. Doesn't take a lot. All you need is, uh, people are more than 42:55.980 --> 43:00.940 happy to put on tables and, uh, you just sit around except for false time, which is a completely 43:00.940 --> 43:07.420 different level of commitment to learning. So let's quickly go through some of the stuff that was 43:07.420 --> 43:13.100 in the mailing list. Very busy monta actually on the mailing list. Uh, it kind of comes and 43:13.100 --> 43:21.020 goes like that. Um, some monsters, nothing. And then, some monsters, massive, massive discussions. 43:21.020 --> 43:27.180 This month happened to be a massive discussion mont. Uh, oops. And it's centered around, we had 43:27.180 --> 43:34.220 basically three topics for discussion, um, during the last community news. Uh, the first thing that 43:34.220 --> 43:41.260 we discussed was releasing the backup shows. Um, we do have, if you go to the HP or website 43:42.460 --> 43:49.180 one second, one second. Yeah, if you go to the HP or website, then at the bottom, you see a list of 43:49.180 --> 43:54.460 backup shows that we have. And we're now calling these emergency shows. So the discussion was 43:54.460 --> 43:59.500 that there was some shows in there. For example, yours, your best eggs in the world has been in 43:59.500 --> 44:05.660 there nearly two years now. So nearly three years. Oh, the discussion was should we release them 44:05.660 --> 44:12.620 or what should we do? What is the backup show? And basically go ahead. I think I've said it before. 44:12.620 --> 44:18.220 So and I don't feel super strongly about it. But I like having the backup queue. I like having 44:18.220 --> 44:23.660 shows in there in case we run low. And I don't mind if someone, if we want to put a limit on the 44:23.660 --> 44:27.660 number of shows in the queue and when someone submits a new one, then, you know, the oldest in 44:27.660 --> 44:33.420 that queue gets filtered into the regular queue. Something like that is fine with me. But I don't 44:33.420 --> 44:38.220 feel so strongly that I'm willing to argue about it. If someone doesn't like the backup queue 44:38.220 --> 44:43.820 and doesn't want it there. So I kind of tend to remain silent on such topics. So that was 44:43.820 --> 44:49.420 one, your side of the argument, my side of the argument was that the backup shows are used as a 44:49.420 --> 44:55.500 crutch to people. That's when the CV queue list going down, they will go, oh, it's fine. I still 44:55.500 --> 45:00.540 have some time to prepare a show on send it in. And invariably people forget the urgency and then 45:00.540 --> 45:06.460 it's left to some old regulars to put in shows. And if we look at the number of shows that there 45:06.460 --> 45:11.180 have been for the last few months, it's been basically the old regulars with a few exceptions. 45:11.180 --> 45:19.500 So people stop having us fill in shows and send them more shows. But the discussion went 45:19.500 --> 45:25.580 too and fro, I think, Dave, do you want to give a summary of what happened in the end? Not sure, 45:25.580 --> 45:30.780 I remember actually, and you probably remember it better than I did. It's a long time ago. 45:31.820 --> 45:40.220 So the discussions when I think is some people wanted to were okay with the idea of releasing 45:40.220 --> 45:44.700 the shows. Basically, I was also saying that some of the shows were gone stale, like, for example, 45:44.700 --> 45:51.340 what's on my podcast player? A lot of the shows may a lot of the stuff that's on your podcast player 45:51.340 --> 45:58.540 will not be as relevant in two years time. And to contract that, plateau says, you have the stuff 45:58.540 --> 46:03.020 that he's putting in as timeless and then therefore should be unused and emergency, which is 46:03.020 --> 46:09.100 which is good because a tattoo has an opinion as well. He has been a person who's been putting 46:09.100 --> 46:15.420 our shows as well when we've been low. So he also knows what it's like to not have a show. So 46:15.420 --> 46:22.460 it's actually what we kind of agreed, I think, is that the emergency show is, the emergency 46:22.460 --> 46:31.740 queue is intended only to be in used when there is still a gap in the 24 hours prior to release. 46:31.740 --> 46:39.900 So we will use that those shows if there is a slot available, not filled within 24 hours of release. 46:39.900 --> 46:49.180 So, for example, on Monday, that the Wednesday slot is available or something like that. 46:50.140 --> 46:54.140 And you should all just give you the exact text from the contribute page. 46:55.580 --> 47:01.100 The emergency queue. The emergency queue is intended only to be used in cases where there is 47:01.100 --> 47:06.460 still a gap in the schedule 24 hours prior to release. The shows will be by their very 47:06.460 --> 47:12.300 nature. They should, sorry, again, the shows will by their very nature need to be timeless. 47:12.860 --> 47:19.340 IE or topic should still be relevant four years or more. People will be able to hear the show 47:19.340 --> 47:24.380 on the website, but they will not be included in any feeds until release. 47:24.380 --> 47:30.620 Please begin all shows with text similar to, I'm talking about emergency shows here. 47:31.260 --> 47:36.780 This is an emergency show. If you are hearing this, then HPR needs shows ASAP. Please 47:36.780 --> 47:42.220 consider contributing show email admin at hackapublicradio.org for more information. 47:43.500 --> 47:45.500 So if you can put that at the beginning, that would be great. 47:45.500 --> 47:51.180 Continuing on, we expect that we need at least 10 shows in the emergency queue in order to give 47:51.180 --> 47:56.780 people time to record and submit shows. Remember that once all the emergency shows have been 47:56.780 --> 48:02.540 used up, and there are no more in the shows in the queue, HPR as a project will stop. 48:03.660 --> 48:04.140 Comments? 48:05.100 --> 48:07.660 No bill keeps getting up and walking away, but before he left, 48:08.940 --> 48:11.100 before he left, I'm bored of you, Bill Emily. 48:11.660 --> 48:15.820 No, no, I'm just walking around talking to people. I always thought that was like a first 48:15.820 --> 48:26.700 in first out 10 show queue. That's what I thought as well, but sentiment on the list seems to 48:26.700 --> 48:33.900 change that. So that is why we're contacted each of the hosts with a show in that queue, 48:34.620 --> 48:39.100 and got clarification from them exactly what it was they wanted to tap on what they're 48:39.100 --> 48:46.300 shows. And now anybody in the queue is there for the very reason that they wanted their show. 48:47.260 --> 48:54.940 Okay, gotcha. And just one other thing. Hold on. When you said that the show should include the text 48:54.940 --> 49:01.420 there, are you, is that going to be a text to speech, and we're going to add that audio to the 49:01.420 --> 49:08.140 six shows that are in that queue? No, I think I'll leave the six shows. I don't know. Might add that to the, 49:10.140 --> 49:15.020 I had intended whoever's recording the show, seen as you're doing a further emergency show, 49:15.020 --> 49:20.460 you put that in. So, might add it to those shows and add it to the, so the only person who 49:20.460 --> 49:26.780 hasn't got back to me with a date that they wanted their show released on was Jesra, how I use Linux. 49:26.780 --> 49:32.540 And by the way, if it wasn't for all these shows been released this month, we wouldn't, 49:32.540 --> 49:37.260 we would have already ran out of shows. By the way, just, just say in folks, just saying. 49:38.700 --> 49:44.540 And I still need to make it so that those shows will be playable from the website post. 49:44.540 --> 49:48.620 I might get that tomorrow, perhaps. Cool. Bruce Patterson's just coming in the room to 49:48.620 --> 49:51.900 want to say hi to you guys, if you don't mind here, it's push the talk, Bruce. It's all in 49:51.900 --> 49:56.380 shift for you. Hey, Ken, what's going on? No, too bad. How are you? Long time no hear. 49:57.260 --> 50:00.380 I'm doing okay. It's taking me a little while to master the keys here. 50:01.100 --> 50:05.980 I know. I've been struggling with that myself. So, when are we going to hear you back on the 50:05.980 --> 50:13.100 airways? I'm semi-retired, actually. I decided that, you know, like anything else, 50:13.100 --> 50:19.020 once something turns into a job, it doesn't become really funny anymore. So, I think it'll be 50:19.020 --> 50:25.180 a little while before I come back. Yes, you see what you need to do is just farm off all these jobs 50:25.180 --> 50:30.540 to other people. But I guess you did that, actually. You're correct about that. In fact, 50:30.540 --> 50:35.900 I've been running around Cambridge today, getting pictures of awful, frank, geary designs. 50:36.460 --> 50:42.940 Okay, cool. Thanks. Well, if you ever want to come on, do do show. There's always a 50:42.940 --> 50:46.860 slot available here for your no-pressure. Won't show you. Anybody could do that? 50:46.860 --> 50:51.740 You know, it's really funny you say that because one of the things I was thinking about is that 50:51.740 --> 50:56.060 at the very minimum, you're right. I actually could do something like that. Because now, 50:56.060 --> 51:01.660 if anything, that's kind of what I have now is a little more time. Yep. It's easy peasy, 51:01.660 --> 51:06.060 lemon squeezy. And besides, I think if anything, one of the things I want to plug on top of 51:06.060 --> 51:13.340 you find folks actually showing up at our Linux Fest every year. I mean, a big round of thanks to, 51:13.340 --> 51:18.780 you know, pokey and new N.Y. Bill and new and for all of the, you know, support. I mean, 51:18.780 --> 51:24.780 you guys were here at the very beginning, even before I was. So, you know, a huge thanks. I mean, 51:24.780 --> 51:29.980 it's support like this that actually makes everything go well. This is actually what I consider 51:29.980 --> 51:35.100 sort of the best as a community, if you will. Oh, thanks very much. There are good guys. I will say, 51:35.100 --> 51:41.420 I always enjoy getting these episodes in because this doesn't know where I can attend much 51:41.420 --> 51:46.540 though I'd like to. I, you know, sorry. Can I forgot to key up you missed that? I said, 51:46.540 --> 51:49.980 you're there, Paul.com. Yeah. And he said, no, it's security weekly now. 51:51.660 --> 51:56.540 Is Paul there? Yes, he is. Dragon over. Okay. Hold on one second. Can you want to say hi? 51:56.540 --> 52:03.100 Yeah. Yeah. Hello, computer. Hello, Paul. Paul, I've been listening to your 52:03.100 --> 52:08.140 at Biden's Ken from the Netherlands or Ireland, depending on your point of view. I can't 52:08.140 --> 52:12.380 tell you. I've been hearing your pimping that you're going to this fest for ages on the 52:12.380 --> 52:18.780 UFO. What are we calling them now? Paul's security weekly. That's right. So, how is life? 52:19.580 --> 52:27.340 Life is good. We moved into a studio in Rhode Island. So, our broadcasts are larger than life now. 52:27.340 --> 52:33.660 And we're doing full internet and radio production in our studio. It's been a lot of fun. 52:33.660 --> 52:40.620 Have you given your talk yet? Um, I'll be giving my talk in about a half an hour or so. 52:40.620 --> 52:45.340 Okay. Very good. Two things. I've done an episode on how to give up smoking. So, if you ever 52:45.340 --> 52:49.420 wonder, refer to that you can. Okay. Yeah. No, thanks. But thanks for offering. 52:51.180 --> 52:54.940 You also do still gig eggs as well. So, yeah. Fat chance there. 52:55.740 --> 53:01.340 Yeah. The story you can show is a lot of fun. You know, they have that show being studio 53:01.340 --> 53:06.620 and being a place where you can actually have a cigar and do a show is pretty epic. We actually 53:06.620 --> 53:11.980 had all four members of the story geeks in studio as Will's in North Carolina, but he made the trip up. 53:11.980 --> 53:17.260 So, um, that was a, a very interesting and entertaining episode. Okay. Cool. So, 53:17.260 --> 53:22.780 for a good look with your talk. Thank you very much. Security weekly. Say it with me now. 53:22.780 --> 53:28.380 Security weekly. Thank you. Paul, that comes. Here's weekly. Paul, that comes. 53:28.380 --> 53:33.020 Excuse me. Yes, it's going to take me a while to get that into my brain. I have to say 53:34.300 --> 53:38.860 anyone else over there? Well, I'm sorry, Ken. Is there anyone else wants to talk or 53:38.860 --> 53:44.300 shall I continue on with the mailing list? Yeah, X111's on his way over. Oh, cool. 53:45.100 --> 53:50.860 And Jeff and Ken, if you could, could you please email me, Richard Quirin's email address, 53:50.860 --> 53:58.860 because Paul's asking about the design of our, our banner. And that was him, I believe. Oh, yes. You're 53:58.860 --> 54:06.700 going to have to email me to remind me about that, of course. Yeah, okay. Hello, everyone. This is X111-01. 54:07.500 --> 54:13.500 How's it going? X111-01. Go ahead over. What's happening over there? What have you been 54:13.500 --> 54:18.940 doing? Uh, I made a trip down about a three hour trip down to spend the day at the Hacker Public 54:18.940 --> 54:27.260 Radio table. So you're a Hacker Public Radio listener, then, would you be? Yeah, for about nine, 54:27.260 --> 54:33.580 ten months now? Very good. So I figured I would show you a show. And so I've made one today. 54:33.580 --> 54:37.820 Excellent. I was going there. I was going there. So what's your show on? 54:38.620 --> 54:45.180 The obligatory, how I got into Linux? Fantastic. I do do like those. I just realized we're going 54:45.180 --> 54:50.220 through the, I wanted to clean up the website. I wanted to clean up the number of series. And 54:50.220 --> 54:58.620 there's definitely a lot more how I got into Linux shows than a sign that. So I would appreciate 54:58.620 --> 55:06.460 anybody listening who's got some time on their hands to help us clean out the episodes to put 55:06.460 --> 55:10.940 the shows on the right episodes. So it'd be great. So you've been on the boot the whole time. You 55:10.940 --> 55:15.660 have to be in a ton of talks at all. Not yet. I am planning on going to Paul's talk, but I haven't 55:15.660 --> 55:21.100 been any other talks. Missing at the table with the, with the gang here. And how have you been 55:21.100 --> 55:27.420 funding it? Is everything I thought it would be in more? Yeah, cool. This is a nice banner just to be said. 55:28.460 --> 55:33.340 Yeah, it's wicked nice. That banner is awesome. It still has that new vinyl smell. 55:33.340 --> 55:39.740 Yeah, the only thing is people were asked me about, you know, are you a radio show? So I would 55:39.740 --> 55:46.060 possibly, if I was doing it again, just put a community driven into that radio. Yeah, I could 55:46.060 --> 55:52.060 get actually that works, into that radio. That's actually that works very well. So if you don't mind 55:52.060 --> 56:01.020 our continued on with the mailing list right on, we had someone asking about the mobile number 56:01.020 --> 56:09.020 and that was March. Yes, sigflow was asking about the mobile server and details for that are on the 56:09.020 --> 56:15.740 contribute page. David Twittman was talking about the, yeah, the backup shows and that's 56:15.740 --> 56:23.820 sort of thing. Yeah, he also requested that we reserve a slot for the 8th of July. And obviously 56:23.820 --> 56:30.540 nobody had a problem with that. Then I posted the question, how useful the community news show was. 56:31.820 --> 56:38.220 Very. And yeah, unfortunately, everybody seems to think very, so we continue doing that. 56:38.220 --> 56:44.300 But if people have, have suggestions first, please send them along. This one's going to be 56:44.300 --> 56:51.020 very long. Also, if you like the community news show, you join it. Everyone's in a while. You 56:51.020 --> 56:57.260 need to be here every month, but you know, help out. Yes, exactly. And if you are in a time zone 56:57.260 --> 57:02.780 or at a time that doesn't suit you, then then, you know, we can switch the times. I don't need to 57:02.780 --> 57:11.580 be on that every month, not at all, or if you wish, you can send in your contribution, be email. 57:11.580 --> 57:18.940 Also, send us a recording, which we can include in. If you want that sort of thing, if you want 57:18.940 --> 57:23.820 to pimpe something that's coming up, send that in. And that this is the show that I'd like to 57:23.820 --> 57:31.100 get all that stuff on. If you have any comments or, you know, you can send in a recording and 57:31.100 --> 57:38.220 we'll let it in whatever is in that recording happens. I'm actually shutting down now, so we better 57:38.220 --> 57:42.460 finish this thing off. But if you have any suggestions for how we can improve the community news 57:42.460 --> 57:48.220 or what we should do with the community news, give us a shot. Then we had a loss about, actually, 57:48.220 --> 57:55.420 that was the rest is referring to more or less April. So that's pretty much it from the mailing list 57:55.420 --> 58:00.540 this month. Yeah, next month's new show is going to be fun. April went fun so far. 58:00.540 --> 58:06.700 There was one other thing, which was, yeah, should we fix a slot for the community news? And that 58:07.900 --> 58:16.380 that I think has been, yeah, yes, as well. So let's do that. So yeah, if anyone also has some ideas 58:16.380 --> 58:22.540 and how we can improve things, you know, feel free to give us a shout. That is the point you 58:22.540 --> 58:29.580 are the community. Yeah, that's a really good point. Sometimes I think might not be made enough, 58:29.580 --> 58:37.420 is that you, the listener are the community. And we, the community are the producers of HPR. So 58:37.420 --> 58:43.180 if you're listening, you're involved and we just need you to be involved a little more or just 58:43.180 --> 58:48.700 slightly differently and, you know, help to produce the content. Yeah, exactly. And that's you. 58:49.500 --> 58:55.180 You, over there. And it's not, you know, there's no guarantee I'm going to jump on. I don't 58:55.180 --> 59:01.660 jump on everybody like I do. Like I did poor Dave. So don't worry about that. But even something 59:01.660 --> 59:06.700 like feedback on whether people listen to the community news show, that is very helpful. And you 59:06.700 --> 59:11.580 know what the most helpful thing is to contact the people who have done the shows and just say, 59:11.580 --> 59:16.540 hey, I like your show. Because there is no bigger buzz you can get and it just makes choose you up. 59:18.380 --> 59:23.340 It choose you up. No end. Just getting an email in your mailbox from somebody across the other 59:23.340 --> 59:25.740 side of the world going, hey, thanks very much for that episode. 59:26.700 --> 59:31.260 Absolutely. Well, Poké, anything else that you want to say? 59:34.300 --> 59:38.940 No, I think I'm good. Just, uh, Northeast Linux Fest is a lot of fun. Conferences are a lot of fun. 59:39.740 --> 59:44.940 Host in the HPR table is a lot of fun. And you should give it a try. Come to Northeast Linux Fest next 59:44.940 --> 59:50.220 year. Yes, I think we will. I think it will. Somebody wants to send me the money. Actually, 59:50.220 --> 59:54.860 don't because the better uses for the money than send in my big fat hours over across to the 59:54.860 --> 01:00:01.660 America. Can you should build a money making machine out of a Raspberry Pi that will just, you know, 01:00:01.660 --> 01:00:07.020 generate pennies just for a while until you get it. Yeah, Bitcoin. We need a Kencoin. Yeah, 01:00:07.020 --> 01:00:12.060 we'll generate those. Yeah, I'm right on this. Okay, guys, if there's nothing else, Dave, are you 01:00:12.060 --> 01:00:16.380 still around? I'm still here, Ken. You want to mention something about series, you said? 01:00:16.380 --> 01:00:22.540 Oh, yeah, I do kind of mention it. I'd like the series to be cleaned up. It's an absolute mess. 01:00:22.540 --> 01:00:28.700 If you look in the series page, there's basically loads of series with one episode in it. And then 01:00:28.700 --> 01:00:34.060 there are other shows that should be in particular series, like the how I got into Linux series. 01:00:34.060 --> 01:00:40.940 And they're not there. If to somebody who has a brain for that sort of thing, go to the 01:00:40.940 --> 01:00:48.780 HP or website and go to the complete episode guide. And then on another window, go to the 01:00:48.780 --> 01:00:55.260 episode, you know, the mini series page. And do a little bit of matching. And just send me an email 01:00:55.260 --> 01:01:00.540 gone. This episode should be in this series. This series should be gone. This should be changed. 01:01:00.540 --> 01:01:06.140 This, this spelling is wrong. I'm any sorts of corrections at all on the series that would 01:01:06.140 --> 01:01:13.020 really help because it's a mess. You have just reminded me, Ken, another thing that we sort of need 01:01:13.020 --> 01:01:22.860 for the conference kit is, and I do not remember how the how we got the QR code books printed out. 01:01:22.860 --> 01:01:30.140 But the latest show in the QR code book that we send around to the conferences is like 700 01:01:30.140 --> 01:01:36.620 something. So it's, we're missing about half the shows. All right, yeah. That's that's available 01:01:36.620 --> 01:01:43.820 on the, that's a PHP page that's available on the website. So yeah, stop me. I'm email about that. 01:01:43.820 --> 01:01:50.940 What you, what you actually want with that. Okay. And also they, they booked the booklet that I 01:01:50.940 --> 01:01:57.980 hooketed. If somebody wants to give that some lower than attention, maybe some stats and stuff 01:01:57.980 --> 01:02:02.620 in there will be handy because we do have a stats page that could be integrated into that 01:02:02.620 --> 01:02:08.380 in some way. Just make that a like a PDF that you could go to forward slash something or other. 01:02:08.380 --> 01:02:14.860 And download the latest PDF with, you know, all the stats and the number of hours and that's 01:02:14.860 --> 01:02:20.860 sort of the thing. Number of hosts. Yeah, a number of downloads. If we could have that, you know, 01:02:20.860 --> 01:02:25.740 the like our average downloads handy for conference time because people always ask. Yeah, 01:02:25.740 --> 01:02:33.100 so there's a complete zip file report.tgz on the website. I haven't run it in a while. I'll update 01:02:33.100 --> 01:02:40.060 it now for this episode. Yeah, that'll be cool. Not that too much use now, but for the next one. 01:02:40.060 --> 01:02:45.260 Yeah, yeah. And now I'm good. We know how I'm talking about like a checklist as well for 01:02:45.260 --> 01:02:50.700 going to the shows. I know I kind of have it in my head while I need to bring, but it's, it's 01:02:50.700 --> 01:02:56.620 kind of useful to have a checklist. And if there's always people who can, you know, print off stickers 01:02:56.620 --> 01:03:02.780 and stuff that would be cool. And mugs with my face in it. Hard, hard, hard, hard, hard. 01:03:04.220 --> 01:03:07.420 Okay. If you don't have a drink in problem now, you will. 01:03:09.260 --> 01:03:15.820 Okay, guys, unless there's anything else, I think we call it a day. Okay, see you later. 01:03:15.820 --> 01:03:21.100 All right. All right, goodbye, everybody. And remember, it's now traditional to singing the 01:03:21.100 --> 01:03:24.940 free software song. I'm not singing, goodbye, everybody. 01:03:24.940 --> 01:03:35.180 And share the software, you'll be free hackers, you'll be free. I can hear you dancing. If 01:03:35.180 --> 01:03:41.260 you didn't dance, we'd sing. Tune in tomorrow for another exciting episode to all. 01:03:41.260 --> 01:03:52.300 You sit. Hacker public freedom. You have been listening to Hacker public radio where 01:03:52.300 --> 01:03:57.660 Hacker public radio does are. We are a community podcast network that releases shows 01:03:57.660 --> 01:04:02.940 every week that you want to get your Friday. Today's show, like all our shows, was contributed 01:04:02.940 --> 01:04:09.180 by a HPR listener like yourself. If you ever consider recording a podcast, then visit our website 01:04:09.180 --> 01:04:14.380 to find out how easy it really is. Hacker public radio is found by the digital.com 01:04:14.380 --> 01:04:19.420 and the information computer below. HPR is funded by the binary revolution 01:04:19.420 --> 01:04:24.460 at binref.com. All binref projects are crowded sponsored by linear pages. 01:04:25.580 --> 01:04:31.340 From shared hosting to custom private clouds, go to lunar pages.com for all your hosting needs. 01:04:31.340 --> 01:04:39.100 On this otherwise stages, today's show is released on your created comments, attribution, share 01:04:39.100 --> 01:05:00.380 a life the digital life is.